The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

src/BaseSelect/index.tsx (1)

386-386: 行为差异提醒：useMergedState → useControlledState 可能限制“受控/非受控切换”

• useControlledState 通常在首渲染锁定“是否受控”，后续不鼓励从非受控切换为受控（或反之）。若外部对 open 存在动态切换（从 undefined 变为 boolean 或相反），可能与旧实现的宽松行为不同，产生不可预期状态。
• 当前初始化 defaultOpen || false 语义与旧逻辑等价，OK。

为降低误用风险，可在开发环境做一次警告封装（仅示意）：

-const [innerOpen, setInnerOpen] = useControlledState<boolean>(defaultOpen || false, open);
+const [innerOpen, setInnerOpen] = useControlledState<boolean>(defaultOpen || false, open);
+if (process.env.NODE_ENV !== 'production') {
+  const controlledRef = React.useRef(open !== undefined);
+  React.useEffect(() => {
+    if (controlledRef.current !== (open !== undefined)) {
+      // eslint-disable-next-line no-console
+      console.warn('[BaseSelect] `open` 从受控切换到非受控（或相反）不被支持，请固定用法。');
+    }
+  }, [open]);
+}

另：微建议将 defaultOpen || false 改为更直观的 Boolean(defaultOpen)。

请补一例用例覆盖：

• 仅传 defaultOpen（非受控）；
• 传 open（受控）；
• 模拟从未传 open → 传入 open 的切换（应得到预期警告/行为）。

src/Select.tsx (1)

275-276: 移除 postState 后的空值归一化差异：请确认不会传入 null

原先 useMergedState('', { value: searchValue, postState: v => v || '' }) 会把 undefined/null 归一为 ''。现在 useControlledState('', searchValue) 若外部误传 null，mergedSearchValue 可能为 null，进而影响字符串操作与过滤逻辑。

若希望保持兼容，可在取值处做一次兜底归一（不改变受控判定）：

-const [mergedSearchValue, setSearchValue] = useControlledState('', searchValue);
+const normalizedSearchValue = (searchValue as string | undefined) ?? '';
+const [mergedSearchValue, setSearchValue] = useControlledState('', normalizedSearchValue);

或者在使用点统一 (mergedSearchValue || '')。请结合现有用例选择其一，并补充测试覆盖 searchValue: undefined/null/''。

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro